home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d8
/
xrs34ovl.arc
/
XRS34OVL.DOC
< prev
Wrap
Text File
|
1990-07-16
|
2KB
|
45 lines
Note: The XRS overlayed versions are bumping up against the limit of static
data allowed in a program (64k), so I had to cut the outbound message limit
down to 90 (it used to be 99) when I added support for 72-character subject
fields (which ate up a good bit of remaining static data table space).
XRS will soon be linked with RTLink+ 3.1 (and later RTLink+ 4.0 with "VML")
so that a single version will run either overlayed or not depending on what
size and type of memory is available. It will be possible to run XRS 4.00+
versions (probably betas before that!) in less than 200k of available RAM!
The RTLink'd versions will cache overlays in LIM/EMS or XMS 2.0-compatible
extended memory. If you are a registered user, announcements of these new
versions will be made in the "QMX_XRS" support conference when they become
available...
For those of you into the technical aspects of the program, the XRS overlay
requirements of the current versions are:
Executable Load Size Savings
------------ ------- -------
RESP_OVL.EXE 176336 65k
RESP2OVL.EXE 175312 63k
RESP3OVL.EXE 192508 45k
Note that the "Load Size" is the minimum free RAM just to load the program
itself and does *not* include dynamic memory requirements! The minimum RAM
required for normal program functions is 100k - slightly more when you use
43-, 50- or 60-line modes, and more with increasingly larger mailbags. You
can probably run in less memory than this, but certain functions may not be
available, and certain functions will automatically lock themselves out if
they notice there is insufficient RAM to load the first time you use them.
(For example, if the <F6> pop-up summary/index bombs the first time you use
it due to insufficient RAM, it will lock the <F6> key out permanently.)
The "Savings" given are the amount of RAM needed (less than a corresponding
non-overlayed version).
The "RESP3OVL.EXE" version is *not* a '386-specific version - it is simply
a slightly modified version of RESP2OVL.EXE which does not overlay message
display code, therefore executes quite a bit faster is you can 'afford' the
extra 17k of RAM.